ci: fix node version mismatch in required spec validations#1326
Merged
Conversation
wtrocki
approved these changes
Jun 17, 2026
Member
|
Great catch! thank you for being proactive! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
OpenAPI release started failing on "Validate the FOAS can be used with the Go SDK" step due to:
This started after a change in the Go SDK to bump node version from v20 to v22. Since we used v20 in the workflow setup, it started failing.
Fix: Bump workflow setup to use node v22.
Testing:
Ran openapi release for dev manually against this branch successfully: https://github.com/mongodb/openapi/actions/runs/27685139038
Jira ticket: CLOUDP-414595
Closes #1315
Closes #1314
Closes #1313
Closes #1312